例句與造句

1. Tracing garbage collection cycles are triggered too often if the set of live objects fills most of the available memory; it requires extra space to be efficient.
2. Most high-level programming languages avoid the problem by disallowing pointer arithmetic and casting entirely, and by enforcing tracing garbage collection as the sole memory management scheme.
3. Reference counting is also used in disk operating systems and distributed systems, where full non-incremental tracing garbage collection is too time consuming because of the size of the object graph and slow access speed.
4. Tracing garbage collection is the most common type of garbage collection  so much so that " garbage collection " often refers to tracing garbage collection, rather than other methods such as reference counting  and there are a large number of algorithms used in implementation.
5. Tracing garbage collection is the most common type of garbage collection  so much so that " garbage collection " often refers to tracing garbage collection, rather than other methods such as reference counting  and there are a large number of algorithms used in implementation.
6. It's difficult to find tracing garbage collection in a sentence. 用tracing garbage collection造句挺難的
7. In garbage collection ( both tracing garbage collection and reference counting ), objects are only destroyed when there are no references to them, but finalization may create new references to the object, and to prevent dangling references, object resurrection occurs so the references remain valid.
8. RAII is the standard resource management approach in C + +, but is little-used outside C + +, despite its appeal, because it works poorly with modern automatic memory management, specifically tracing garbage collection : RAII " ties " resource management to memory management, but these have significant differences.
9. In computer programming, "'tracing garbage collection "'is a form of automatic memory management that consists of determining which objects should be deallocated ( " garbage collected " ) by tracing which objects are " reachable " by a chain of references from certain " root " objects, and considering the rest as " garbage " and collecting them.
10. As with manual memory management, and unlike tracing garbage collection, reference counting guarantees that objects are destroyed as soon as their last reference is destroyed, and usually only accesses memory which is either in CPU caches, in objects to be freed, or directly pointed by those, and thus tends to not have significant negative side effects on CPU cache and virtual memory operation.
11. The steps during finalization vary significantly depending on memory management : in manual memory management ( as in C + +, or manual reference counting ), references need to be explicitly destroyed by the programmer ( references cleared, reference counts decremented ); in automatic reference counting, this also happens during finalization, but is automated ( as in Python, when it occurs after programmer-specified finalizers have been called ); and in tracing garbage collection this is not necessary.